5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
- Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-2: Getting Started

Page Positioning


You define sizes and positions for frames and images in output processes just as you do in input and menu processes. The primary difference between screen positioning for a menu or input process and page positioning for an output process, however, relates to the timing of the display. This timing issue is a direct result of the difference in display media for an input process (a screen) versus an output process (a printer).

When displaying an input process, for example, it is a relatively simple matter to add an image that displays before, beside, or perhaps between existing images by refreshing the screen. It is an entirely different matter when those images are committed to paper. You cannot request a printer to back up to print an image beside a previously printed image, or perhaps insert a new image between two printed images.

To overcome this printer limitation, APPX uses a preliminary assembly area for output frames and images called the Print Beside buffer. Various components of the output can be pieced together in the buffer before they are committed to paper. A buffer permits you to insert images before or beside existing images, much as you do when displaying to a screen. See the Print Beside section for details.

If you do not use a Print Beside buffer in your output process, each image is immediately committed to the print file during execution. As a result, each image must print below the previous image (unless, of course, a new page is started).

Application Design Manual                                         "Powered by Appx Software"

264

©2006 By APPX Software, Inc. All Rights Reserved